Persistent data storage for a microservices application

ABSTRACT

A device can receive a specification identifying information associated with a stateful microservices application. The device can provide a request for storage information associated with the stateful microservices application based on the information included in the specification. The device can receive the storage information based on providing the request. The device can execute a storage installation procedure to provide the stateful microservices application with a storage volume based on receiving the storage information. The storage volume can be capable of providing persistent data storage. The device can provide a notification that the stateful microservices application is available for deployment on the device based on executing the storage installation procedure.

BACKGROUND

A microservices architecture can refer to a software application thatincludes a suite of independently deployable and modular applicationsthat each executes a unique process and interacts to achieve an overallfunctionality of the software application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are diagrams of an overview of an example implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, can be implemented;

FIG. 3 is a diagram of example components of one or more devices of FIG.2;

FIG. 4 is a flow chart of an example process for utilizing storagevolumes on a set of nodes that collectively host a microservicesapplication to provide persistent location-independent data storage;

FIGS. 5A and 5B are diagrams of an example implementation relating tothe example process shown in FIG. 4; and

FIGS. 6A-6C are diagrams of an example implementation relating to theexample process shown in FIG. 4.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

A microservices application can include an application that includes aset of applications (e.g., microservices) that each performs aparticular functionality of the microservices application, and that eachinteracts to perform an overall functionality of the microservicesapplication. Microservices, of the microservices application, can beindependently scalable. That is, a first microservice can be associatedwith a first number of instances that are executing, a secondmicroservice can be associated with a second number of instances thatare executing, etc.

In some cases, a cloud platform can host a microservices applicationusing one or more containers (e.g., one or more self-contained executionenvironments). For example, a cloud platform can use one or morecontainers to host a stateless microservices application (e.g., amicroservices application that is stateless might not store data forsubsequent use). As another example, a cloud platform can use one ormore containers to host a stateful microservices application (e.g., amicroservices application that is stateful might store data forsubsequent use). However, hosting a stateful microservices applicationthat provides persistent location-independent data storage can requiremanual provisioning of data storage, or can require duplicate containersthat use additional storage resources.

Implementations described herein allow a microservices managementplatform to provide persistent, location-independent data storage for amicroservices application by intelligently providing storage volumes toa set of computing nodes that host the microservices application. Forexample, the microservices management platform can attach and/or detachstorage volumes from a set of computing nodes to provide storage forsupporting a stateful microservices application. In this case, data canbe provisioned at a particular location associated with a set of storagenodes (e.g., a hard disk drive (HDD)). Furthermore, the microservicesmanagement platform can modify the one or more microservices and/or theset of containers used to host the microservices without any indicationto a user that the hosted microservices application has changed. In thisway, the microservices management platform provides persistent datawhile conserving processing resources and/or network resources byefficiently distributing and redistributing storage volumes relative tousing manual provisioning of data storage and/or duplicate containers tohost a stateful microservices application that provides persistentlocation-independent data storage.

FIGS. 1A and 1B are diagrams of an overview of an example implementation100 described herein. As shown in FIGS. 1A and 1B, exampleimplementation 100 shows a microservices application hosted on amicroservices management platform. As shown in FIGS. 1A and 1B, themicroservices management platform can include a set of computing nodes(e.g., shown as computing node 1 to computing node N), a storagemanagement node, and a set of storage nodes (e.g., shown as storage node1 to storage node M). The set of computing nodes can be used to managecomputing tasks associated with hosting the microservices application,and the storage management node can be used to manage the set of storagenodes that provide storage for the microservices application.

As shown in FIG. 1A, and by reference number 105, the microservicesapplication can provide a specification to storage manager of thecomputing node. For example, an owner of the microservices applicationcan provide (e.g., upload) the microservices application to themicroservices management platform (e.g., by providing an image thatincludes a representation of the source code and/or the binariesassociated with the microservices application), and the microservicesapplication can provide the storage manager with a specification thatincludes information associated with the microservices application. Theinformation included in the specification can include a microservicesapplication identifier, a host internet protocol (IP) address, a valueindicating a quantity of data for supporting the microservicesapplication, a file path, information identifying a storage volumedriver, a storage location within a container, and/or the like.

As shown by reference number 110, the storage manager can provide, to aserver-side data manager of the storage management node, a request forstorage information. For example, the storage manager can provide arequest for storage information based on the information included in thespecification. Storage information can include information used toattach and mount a storage volume (e.g., a shared directory to whichdata can be written to and/or read from), such as an IP address, a portidentifier associated with a storage node that can be selected toprovide data storage for the microservices application, metadataindicating a quantity of data available for storage, and/or the like.

As shown by reference number 115, the server-side data manager candetermine that the request for the storage information is being made forthe first time. For example, the server-side data manager can determinewhether the request for the storage information is being made for thefirst time by comparing the microservices application identifierincluded in the specification to a data structure of microservicesapplication identifiers. If the server-side data manager is unable touse the data structure to locate a corresponding microservicesapplication identifier, the server-side data manager can determine thatthe request for storage information is being made for the first time(e.g., the microservices application was not ever hosted on anothercomputing node). If the server-side data manager is able to use the datastructure to locate a corresponding microservices applicationidentifier, the server-side data manager can determine that themicroservices application was not ever hosted by another computing node.In this case, the server-side data manager can detach the storage volumefrom the other computing node, and can attach the storage volume to thecomputing node from which the request is made, as described furtherherein.

As shown in FIG. 1B, and by reference number 120, the server-side datamanager can obtain the storage information from the set of storagenodes. For example, the server-side data manager can communicate withthe set of storage nodes to determine a particular location wherestorage is available, and can select the particular location to serve asthe storage for the microservices application (e.g., the particularlocation might point to a hard disk drive (HDD) associated with aparticular storage node). As shown by reference number 125, the storagemanager can receive the storage information from the server-side datamanager. For example, the storage manager can receive an IP address ofthe particular storage node, a port identifier associated with theparticular storage node, metadata indicating a quantity of dataavailable for storage, and/or the like.

As shown by reference number 130, the storage manager can execute astorage installation procedure. For example, the storage manager canexecute a storage installation procedure to attach and mount the storagevolume. By attaching and mounting the storage volume, the computing nodethat hosts the microservices application is able to completeconfiguration steps required by the microservices application (e.g.,data can be written to the storage volume and/or read from the storagevolume). As shown by reference number 135, the storage manager cannotify the microservices application that storage is available, therebyallowing the microservices application to deploy on the computing node.

By executing the storage installation procedure to attach and mount thestorage volume, the computing node that hosts the microservicesapplication is able to deploy in a manner that provides persistent datastorage, thereby improving scalability and availability of themicroservices application relative to using local storage of thecomputing node and/or relative to using duplicate storage volumes whichwould waste resources.

As indicated above, FIGS. 1A and 1B are provided merely as an example.Other examples are possible and can differ from what was described withregard to FIGS. 1A and 1B.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, can be implemented. As shown in FIG.2, environment 200 can include client device 210, microservicesmanagement platform 220 hosted within cloud computing environment 230,and network 240. Devices of environment 200 can interconnect via wiredconnections, wireless connections, or a combination of wired andwireless connections.

Client device 210 includes one or more devices capable of providing amicroservices application to microservices management platform 220,receiving updates that the microservices application is ready fordeployment, and/or accessing the microservices application afterdeployment. For example, client device 210 can include a computingdevice, such as a desktop computer, a laptop computer, a tabletcomputer, a handheld computer, a server device, a mobile phone (e.g., asmart phone or radiotelephone), or a similar type of device. In someimplementations, client device 210 can communicate with microservicesmanagement platform 220 to provide the microservices application and/oran update to the microservices application. Additionally, oralternatively, client device 210 can receive updates, from microservicesmanagement platform 220 that the microservices application is ready fordeployment. Additionally, or alternatively, client device 210 can accessthe deployed microservices application while the microservicesapplication is being modified by microservices management platform 220.

Microservices management platform 220 includes one or more computingdevices capable of deploying, configuring, generating, modifying, and/orproviding microservices associated with a microservices application. Insome implementations, microservices management platform 220 can bedesigned to be modular such that certain software components can beswapped in or out depending on a particular need. As such, microservicesmanagement platform 220 can be easily and/or quickly reconfigured fordifferent uses. In some implementations, microservices managementplatform 220 can host a microservices application on a set of computingnodes 222 and/or a set of storage nodes 224 using one or morecontainers, and the one or more containers can be configured to processa microservice (or a task of a microservice), of the microservicesapplication, in a particular way.

In some implementations, as shown, microservices management platform 220can be hosted in cloud computing environment 230. Notably, whileimplementations described herein describe microservices managementplatform 220 as being hosted in cloud computing environment 230, in someimplementations, microservices management platform 220 can be basedoutside of a cloud (i.e., can be implemented outside of a cloudcomputing environment) or can be partially cloud-based.

Cloud computing environment 230 includes an environment that hostsmicroservices management platform 220. Cloud computing environment 230can provide computation, software, data access, storage, and/or otherservices that do not require end-user knowledge of a physical locationand configuration of system(s) and/or device(s) that host microservicesmanagement platform 220. As shown, cloud computing environment 230 caninclude a group of nodes, such as computing nodes 222, storage nodes224, and/or storage management node 226.

While implementations described herein can associate particularfunctionality with particular nodes, any one of the nodes associatedwith cloud computing environment 230 can perform any or all of thefunctionality described herein. Additionally, a single one of thesenodes can, in some implementations, be implemented by multiple nodes.Further, a single one of these nodes can be implemented on a singlecomputing device or can be implemented on multiple computing devices.

Computing node 222 includes one or more devices capable of usingcontainers to host microservices. In some implementations, computingnode 222 can include multiple computing nodes (referred to as a set ofcomputing nodes 222). Additionally, or alternatively, computing node 222can provide one or more tasks associated with microservices to anothercomputing node 222 (e.g., via application programming interface (API)calls). In some implementations, computing node 222 can receive, from amicroservices application, a specification for the microservicesapplication. In some implementations, computing node 222 can implement aclient-side data manager or a container manager to request and/orreceive storage information, and to attach and mount a storage volumebased on the storage information, as described further herein.

Storage node 224 includes one or more devices capable of providing datastorage associated with a microservices application. In someimplementations, storage node 224 can include multiple storage nodes(referred to as a set of storage nodes 224). Storage node 224 caninclude one or more storage systems and/or one or more devices that usevirtualization techniques within the storage systems or devices ofstorage node 224. In some implementations, within the context of astorage system, types of virtualizations can include blockvirtualization and file virtualization. Block virtualization can referto abstraction (or separation) of logical storage from physical storageso that the storage system can be accessed without regard to physicalstorage or heterogeneous structure. The separation can permitadministrators of the storage system flexibility in how theadministrators manage storage for end users. File virtualization caneliminate dependencies between data accessed at a file level and alocation where files are physically stored. This can enable optimizationof storage use, server consolidation, and/or performance ofnon-disruptive file migrations. In some implementations, storage node224 can provide physical storage space for the microservices application(e.g., via one or more hard disk drives (HDDs), one or more solid statedrives (SSDs), etc.), and data written to and/or read from the storagevolume hosted by computing node 222 can be sent over the network to thephysical storage space.

Storage management node 226 includes one or more devices capable ofreceiving, managing, modifying, attaching, detaching, and/or providingstorage information or storage volumes. In some implementations, storagemanagement node 226 can implement the server-side data manager toperform one or more operations associated with data storage. In someimplementations, storage management node 226 can be a computing node222.

As further shown in FIG. 2, computing node 222, storage node 224, and/orstorage management node 226 can include a group of cloud resourcesassociated with an application implementation and/or a containerimplementation, such as one or more microservices, a client-side datamanager, a container manager, a storage volume driver, a server-sidedata manager, one or more containers, or the like.

Microservices include one or more instructions that can be provided toor accessed by client device 210. In some implementations, microservicescan eliminate a need to install and execute the software applications onclient device 210. For example, microservices can include softwareassociated with microservices management platform 220 and/or any othersoftware capable of being provided via cloud computing environment 230.In some implementations, a microservices application can be hosted bycomputing nodes 222 and/or storage nodes 224, using one or morecontainers.

Client-side data manager includes one or more instructions capable ofreceiving, requesting, managing, modifying, attaching, detaching, and/orproviding storage information or a storage volume. In someimplementations, the client-side data manager can receive aspecification of a microservices application. In some implementations,client-side data manager can request and receive storage informationfrom a server-side data manager associated with storage management node226. Additionally, or alternatively, client-side data manager canexecute a storage installation procedure to allow the microservicesapplication to write to and/or read from the storage volume.

Container manager includes one or more instructions capable of allowinga microservices application and its dependencies to be packaged as acontainer. In some implementations, the container manager can receive aspecification of a microservices application, and can provide thespecification to the storage volume driver. Additionally, oralternatively, the container manager can receive storage informationfrom the server-side data manager. Additionally, or alternatively, thecontainer manager can execute a storage installation procedure to allowthe microservices application to write to and/or read from the storagevolume.

Storage volume driver includes one or more instructions that allow thestorage volume driver to request storage information from theserver-side data manager. In some implementations, all (or some) nodesused to host the microservices application can be provisioned with astorage volume driver. In some cases, the storage volume driver can be aplugin for the container manager. In other cases, the storage volumedriver can be included in the operating system kernel.

Server-side data manager includes one or more instructions capable ofreceiving, managing, modifying, attaching, detaching, and/or providingstorage information or storage volumes. In some implementations,server-side data manager can receive a request for storage informationfrom the client-side data manager or the storage volume driver, and canuse the information included in the request to obtain storageinformation from the set of storage nodes 224. In some implementations,server-side data manager can analyze the set of storage nodes 224 todetermine whether a storage volume is available to support amicroservices application. In some implementations, server-side datamanager can provide a request to a first computing node 222 to detach afirst storage volume, and can provide a location associated with thefirst storage volume to a second computing node 222, thereby allowingthe second computing node 222 to attach to the first storage volume.

Containers include a self-contained execution environment that executesprograms like a physical machine. In some implementations, containerscan provide complete support for a microservices application, amicroservice, a task of a microservice, or the like. Additionally, oralternatively, containers can share a kernel associated with a hostoperating system (e.g., the computing node 222 on which the container isdeployed). In some cases, in addition to sharing the kernel of the hostoperating system, containers can share libraries and/or binariesassociated with a microservices application, a microservice, a task of amicroservice, or the like.

Network 240 includes one or more wired and/or wireless networks. Forexample, network 240 can include a cellular network (e.g., a fifthgeneration (5G) network, a fourth generation (4G) network, such as along-term evolution (LTE) network, a 3G network, a code divisionmultiple access (CDMA) network, etc.), a public land mobile network(PLMN), a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a telephone network (e.g., the PublicSwitched Telephone Network (PSTN)), a private network, an ad hocnetwork, an intranet, the Internet, a fiber optic-based network, a cloudcomputing network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 2 areprovided as an example. In practice, there can be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 2. Furthermore, two or more devices shown in FIG. 2 can beimplemented within a single device, or a single device shown in FIG. 2can be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 200 can perform one or more functions described as beingperformed by another set of devices of environment 200.

FIG. 3 is a diagram of example components of a device 300. Device 300can correspond to client device 210 and/or microservices managementplatform 220. In some implementations, client device 210 and/ormicroservices management platform 220 can include one or more devices300 and/or one or more components of device 300. As shown in FIG. 3,device 300 can include a bus 310, a processor 320, a memory 330, astorage component 340, an input component 350, an output component 360,and a communication interface 370.

Bus 310 includes a component that permits communication among thecomponents of device 300. Processor 320 is implemented in hardware,firmware, or a combination of hardware and software. Processor 320includes a central processing unit (CPU), a graphics processing unit(GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor (DSP), a field-programmablegate array (FPGA), an application-specific integrated circuit (ASIC), oranother type of processing component. In some implementations, processor320 includes one or more processors capable of being programmed toperform a function. Memory 330 includes a random access memory (RAM), aread only memory (ROM), and/or another type of dynamic or static storagedevice (e.g., a flash memory, a magnetic memory, and/or an opticalmemory) that stores information and/or instructions for use by processor320.

Storage component 340 stores information and/or software related to theoperation and use of device 300. For example, storage component 340 caninclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 350 includes a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 350 caninclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 360 includes a component that providesoutput information from device 300 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 370 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 300 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 can permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 can include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 can perform one or more processes described herein. Device300 can perform these processes in response to processor 320 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 330 and/or storage component 340. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 can causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 canperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a flow chart of an example process 400 for utilizing storagevolumes on a set of nodes that collectively host a microservicesapplication to provide persistent location-independent data storage. Insome implementations, one or more process blocks of FIG. 4 can beperformed by computing node 222. In some implementations, one or moreprocess blocks of FIG. 4 can be performed by another device or a groupof devices separate from or including computing node 222, such as clientdevice 210, storage node 224, and/or storage management node 226.

As shown in FIG. 4, process 400 can include receiving, by a device, aspecification identifying information associated with a microservicesapplication (block 410). For example, computing node 222 (e.g., aclient-side data manager or a container manager) can receive, from themicroservices application, a specification identifying informationassociated with the microservices application. In some implementations,a client-side data manager can analyze the specification and requeststorage information used to support the microservices application, asdescribed further herein. In some implementations, a container managercan analyze the specification, and can interact with a storage driver torequest storage information used to support the microservicesapplication, as described further herein. In some implementations, themicroservices application is a stateful microservices application.

In some implementations, client device 210 can provide (e.g., upload) amicroservices application to microservices management platform 220,which can be sent to a set of computing nodes 222 and/or a set ofstorage nodes 224 that are selected to host the microservicesapplication. For example, source code and/or binaries associated withthe microservices application can be obtained from a global repository,and can be sent to the set of computing nodes 222 and/or the set ofstorage nodes 224.

In some implementations, computing node 222 (e.g., a client-side datamanager) can receive a specification identifying information associatedwith a microservices application. For example, computing node 222 canhost a microservices application that uses a plugin, and the client-sidedata manager hosted on computing node 222 can receive the specificationfrom the microservices application via API calls enabled by the plugin.The specification can include information associated with themicroservices application, such as a microservices applicationidentifier, a host internet protocol (IP) address, a value indicating aquantity of data storage available for supporting the microservicesapplication, a file path, and/or the like.

In some implementations, computing node 222 can host a microservicesapplication as-is (e.g., without the microservices application using aplugin), and a container manager hosted on computing node 222 canreceive the specification of the microservices application. Thespecification can include information associated with the microservicesapplication, such as a microservices application identifier, informationidentifying a storage volume driver, a value indicating a quantity ofdata for supporting the application, a storage location within acontainer, and/or the like.

In this way, computing node 222 can receive a specification identifyinginformation associated with a microservices application.

As further shown in FIG. 4, process 400 can include providing a requestfor storage information associated with the microservices applicationbased on the information included in the specification (block 420). Forexample, computing node 222 (e.g., the client-side data manager or astorage volume driver associated with the container manager) cangenerate a request for storage information based on the informationincluded in the specification and computing node 222 can provide therequest to a server-side data manager hosted by storage management node226. Storage information can include information associated withmounting a storage volume, such as an IP address and/or a portidentifier associated with a storage node 224 that has been selected toprovide data storage for the microservices application, metadataindicating a quantity of data available for storage, a storagenetworking protocol for managing data associated with the storagevolume, and/or the like. A storage volume can provide storage forsupporting the microservices application (e.g., or a microservice of themicroservices application), and the microservices application can writedata to the storage volume. For example, the storage volume can be ashared directory that is accessible by one or more containers that hostthe microservices application. In some cases, the storage volume canpersist even if the one or more containers hosting the microservicesapplication are removed.

In some implementations, computing node 222 (e.g., the client-side datamanager) can request storage information from a server-side datamanager. For example, computing node 222 can provide a request forstorage information that includes information included in thespecification, such as the host IP address, the quantity of data forsupporting the microservices application, or the like, and theinformation included in the specification can be used by the server-sidedata manager when processing the request.

In some implementations, computing node 222 (e.g., the containermanager) can provide the information included in the specification tothe server-side data manager. For example, the container manager canprovide the information included in the specification to the storagevolume driver, which can cause the storage volume driver to communicatewith the server-side data manager to request the storage information.

Additionally, the request for the storage information can cause storagemanagement node 226 (e.g., the server-side data manager) to obtain thestorage information from a set of storage nodes 224. For example, theserver-side data manager can analyze the set of storage nodes 224 todetermine whether storage is available, and if storage is available, theserver-side data manager can select a storage node of the set of storagenodes to provide the storage. In this case, the server-side data managercan obtain storage information associated with the selected storagenode, such as an IP address and/or a port identifier associated with thestorage node, metadata indicating a quantity of data available forstorage, or the like.

In some cases, the server-side data manager can analyze the set ofstorage nodes 224 with a scoring technique. For example, the server-sidedata manager can use a scoring technique to analyze each storage node224, in the set of storage nodes 224, to determine a particular storagenode 224 to select for supporting the data storage of the microservicesapplication. In this case, the scoring technique can consider a set offactors, such as a load associated with a storage node 224, a totalcapacity of a storage node 224, an amount of available capacity of astorage node 224, a physical location of a storage node 224, one or moreperformance capabilities of a storage node 224, whether storage node 224has enough data storage available to satisfy the request made in thespecification, a time period in which storage node 224 has been active,one or more types of storage available on storage node 224 (e.g., HDD,SSD, etc.), an amount of available bandwidth of one or more links tostorage node 224, and/or the like. In some cases, the set of factors canbe weighted, allowing the server-side data manager to prioritize certainfactors.

Additionally, the request for storage information can cause theserver-side data manager to determine whether the microservicesapplication is deployed to another computing node 222 or whether themicroservices application is requesting to be deployed for the firsttime. For example, the server-side data manager can determine whetherthe microservices application is deployed because deployed microservicesapplications have microservices application identifiers stored in a datastructure. In this case, the server-side data manager can compare themicroservices application identifier to the data structure ofmicroservices application identifiers.

In some cases, if the server-side data manager is unable to use the datastructure to locate a corresponding microservices applicationidentifier, the server-side data manager can determine that the requestfor storage information is being made for the first time. In this case,the server-side data manager can select a storage node 224 of the set ofstorage nodes 224 to provide storage for the microservices application,in the manner described above.

In other cases, if the server-side data manager is able to use the datastructure locate a corresponding microservices application identifier,the server-side data manager can determine that that microservicesapplication is deployed to another node. In this case, the server-sidedata manager can detach the storage volume from the other node, based ondetermining that the microservices application is deployed on the othernode. Furthermore, computing node 222 can receive, from storagemanagement node 226, an indication that the storage volume is detachedfrom the other node. Additionally, computing node 222 can provide, tostorage management node 226, a request to attach the storage volume. Therequest to attach the storage volume can cause storage management node226 to obtain the storage information, as described above.

By determining whether the microservices application is deployed toanother node or is requesting to deploy for the first time, and byanalyzing the set of storage nodes 224 to determine if storage isavailable, microservices management platform 220 efficiently andeffectively utilizes network resources.

In this way, computing node 222 can provide a request for storageinformation, associated with the microservices application, based on theinformation included in the specification.

As further shown in FIG. 4, process 400 can include receiving thestorage information based on providing the request (block 430). Forexample, the client-side data manager or the container manager ofcomputing node 222 can receive the storage information from theserver-side data manager of storage management node 226. In some cases,the client-side data manager can receive the storage information, whichcan trigger the client-side data manager to execute a storageinstallation procedure, as described further herein. In other cases, thecontainer manager can receive the storage information, which can triggerthe container manager to execute a storage installation procedure, asdescribed further herein.

In this way, computing node 222 can receive the storage informationbased on providing the request.

As further shown in FIG. 4, process 400 can include executing a storageinstallation procedure to provide the microservices application withstorage based on receiving the storage information (block 440). Forexample, computing node 222 (e.g., the client-side data manager, thecontainer manager, etc.) can execute a storage installation procedure toallow the microservices application to access (e.g., write to, readfrom, etc.) a storage volume. The storage installation procedure canconfigure computing node 222 in a manner that allows computing node 222to support traffic flow (e.g., data) from computing node 222 to astorage node 224 of a set of storages nodes 224. The storageinstallation procedure can use the storage information to attach astorage volume and to mount the storage volume. Attaching the storagevolume can refer to a process in which a logical connection is createdfrom the storage volume to a hypervisor hosting computing node 222(e.g., using an internet small computer systems interface (i SC SI)protocol). Mounting the storage volume can refer to a process in whichcomputing node 222 makes a file system available on computing node 222.In some cases, the mount process can instruct an operating system on howto logically map a file system structure to a physical storage device,such as an HDD of storage node 224. In some cases, the mount cangenerate a directory, accessible on computing node 222, and dataassociated with the microservices application can be written to thedirectory. In some cases, the storage volume can be capable of providingpersistent data storage.

In some implementations, computing node 222 (e.g., the client-side datamanager) can execute a storage installation procedure. For example, theclient-side data manager can establish a path between computing node 222and a storage node 224 that is hosting the storage volume. In this case,the path can allow traffic associated with the storage volume to be sentto a location within the storage node 224 that is hosting the storagevolume (e.g., a particular HDD). Additionally, computing node 222 canmount the storage volume based on establishing the path.

In some implementations, computing node 222 (e.g., the containermanager) can execute a storage installation procedure. For example,computing node 222 can attach the storage volume to computing node 222using an IP address and/or a port identifier associated with aparticular storage node 224, and computing node 222 can generate a filesystem on the storage volume based on the attachment. In this case,computing node 222 can mount the storage volume to an operating systemof computing node 222 based on generating the file system. Additionally,computing node 222 can mount the storage volume to a containerassociated with computing node 222 based on mounting the storage volumeto the operating system. In this way, computing node 222 is able towrite data to and/or read data from the storage volume that is hosted bystorage node 224, thereby providing persistent data storage.

In this way, computing node 222 may execute a storage installationprocedure to provide the microservices application with storage based onreceiving the storage information.

As further shown in FIG. 4, process 400 can include providing anotification that the microservices application is available fordeployment on the device, based on executing the storage installationprocedure (block 450). For example, computing node 222 (e.g.,client-side data manager, container manager, etc.) can provide anotification that the microservices application is available fordeployment, thereby allowing the microservices application to deploy oncomputing node 222.

In some implementations, such as after the microservices applicationdeploys, computing node 222 (e.g., the client-side data manager, thecontainer manager, etc.) can determine whether traffic associated withthe storage volume satisfies a threshold, and computing node 222 canrequest and receive additional storage based on determining whether thetraffic associated with the storage volume satisfies the threshold. Forexample, assume computing node 222 receives an indication that themicroservices application has been deployed. Further assume computingnode 222 receives traffic associated with client device 210 writing datato the storage volume. In this case, computing node 222 can determinethat the traffic satisfies a threshold, which can cause computing node222 to provide a request, to storage management node 226, for additionalstorage information. The request can trigger storage management node 226to obtain the additional storage information from the set of storagenodes 224. In this way, computing node 222 is able to obtain theadditional storage volume in the same manner (or in a similar manner)that was used to obtain the storage volume.

Additionally, computing node 222 can receive, from storage managementnode 226, the additional storage information and can execute anotherstorage installation procedure to support the additional storage. Forexample, computing node 222 can receive, from storage management node226, the additional storage information, which can cause computing node222 to execute another storage installation procedure. In this case,computing node 222 can attach another storage volume, and can mount theother storage volume based on the attachment. By determining that thestorage volume satisfies a threshold (e.g., reaches a particularcapacity), and by obtaining an additional storage volume based on thedetermination, computing node 222 ensures persistent data storage.

In this way, computing node 222 can provide a notification that themicroservices application is available for deployment based on executingthe storage installation procedure.

Although FIG. 4 shows example blocks of process 400, in someimplementations, process 400 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 4. Additionally, or alternatively, two or more of theblocks of process 400 can be performed in parallel.

In this way, microservices management platform 220 provides persistentdata while conserving processing resources and/or network resources byefficiently distributing and redistributing storage volumes.

FIGS. 5A and 5B are diagrams of an example implementation 500 relatingto example process 400 shown in FIG. 4. As shown in FIGS. 5A and 5B,example implementation 500 shows a stateful microservices applicationhosted on microservices management platform 220. As shown in FIGS. 5Aand 5B, microservices management platform 220 can include a set ofcomputing nodes 222 (e.g., shown as computing node 1 to computing nodeN), storage management node 226, and a set of storage nodes 224 (e.g.,shown as storage node 1 to storage node M). In this case, the statefulmicroservices application can include a plugin to allow themicroservices application to communicate with a client-side datamanager.

As shown in FIG. 5A, and by reference number 505, the statefulmicroservices application can provide a specification to the client-sidedata manager. The specification can include information associated withthe stateful microservices application, as described above. As shown byreference number 510, the client-side data manager can provide, to aserver-side data manager, a request for storage information. Forexample, the client-side data manager can provide a request for storageinformation, where the request includes a microservices applicationidentifier.

As shown by reference number 515, the server-side data manager candetermine that the request for storage information is being made for thefirst time. For example, the server-side data manager can determine thatthe request for storage is being made for the first time by comparingthe microservices application identifier included in the specificationto a data structure of microservice application identifiers. In thiscase, assume the server-side data manager is unable to use the datastructure to locate a corresponding microservices applicationidentifier, which causes the server-side data manager to determine thatthe request for storage information is being made for the first time.

As shown in FIG. 5B, and by reference number 520, the server-side datamanager can obtain the storage information from the set of storage nodes224. For example, the server-side data manager can communicate with theset of storage nodes 224 to determine a particular location wherestorage is available (e.g., a HDD of a particular storage node 224), andcan select the particular location as the location to serve as thestorage for the stateful microservices application. As shown byreference number 525, the client-side data manager can receive thestorage information from the server-side data manager. For example, theclient-side data manager can receive an IP address of the particularstorage node 224, a port identifier associated with the particularstorage node 224, metadata indicating a quantity of data available forstorage, and/or the like.

As shown by reference number 530, the client-side data manager canperform a storage installation procedure. For example, the client-sidedata manager can establish a path to the particular storage node 224that is hosting the storage volume, based on the IP address and/or theport identifier associated with the particular storage node 224. In thiscase, the path can allow data written to the storage volume to be sentto a location within the particular storage node 224 (e.g., a HDD).Furthermore, the client-side data manager can mount the storage volumebased on establishing the path. As shown by reference number 535, theclient-side data manager can notify the stateful microservicesapplication that storage is available.

By providing the microservices application with a plugin to communicate(e.g., via API calls) with the client-side data manager, and using theclient-side data manager to obtain storage information that can be usedto mount the storage volume, computing node 222 provides persistent datastorage.

As indicated above, FIGS. 5A and 5B are provided merely as an example.Other examples are possible and can differ from what was described withregard to FIGS. 5A and 5B.

FIGS. 6A-6C are diagrams of an example implementation 600 relating toexample process 400 shown in FIG. 4. As shown in FIGS. 6A-6C, exampleimplementation 600 shows a stateful microservices application hosted onmicroservices management platform 220. As shown in FIGS. 6A-6C,microservices management platform 220 can include a set of computingnodes 222 (e.g., shown as computing node 1 to computing node N), storagemanagement node 226, and a set of storage nodes 224 (e.g., shown asstorage node 1 to storage node M). In this case, the statefulmicroservices application can be deployed as-is (e.g., without aplugin).

As shown in FIG. 6A, and by reference number 605, a container managercan receive a specification from the stateful microservices application.The specification can include information associated with the statefulmicroservices application, such as a microservices applicationidentifier, information identifying a storage volume driver, a valueindicating a quantity of data storage available for supporting theapplication, a storage location within a container, and/or the like. Asshown by reference number 610, the container manager can use theinformation identifying the storage volume driver to provide thespecification to storage volume driver A. As shown by reference number615, storage volume driver A can provide a request for storageinformation to a server-side data manager. For example, storage volumedriver A can provide a request for storage information that includes themicroservices application identifier included in the specification.

As shown in FIG. 6B, and by reference number 620, the server-side datamanager can determine that the storage volume is attached to anothernode. For example, the server-side data manager can compare themicroservices application identifier to a data structure ofmicroservices application identifiers. In this case, assume theserver-side data manager is able to use the data structure to locate acorresponding microservices application identifier, which causes theserver-side data manager to determine that the storage volume isattached to another node. In this case, the microservices applicationidentifier can be stored in the data structure in a manner thatassociates the microservices application identifier with an IP addressand/or a port identifier of a computing node 222 and/or a storage node224 that is presently supporting the microservices application (e.g.,shown as computing node 2). As shown by reference number 625, theserver-side data manager can detach the storage volume from computingnode 2. In this case, and as shown by reference number 630, storagevolume driver A can receive a notification that the detachment iscomplete.

As shown in FIG. 6C, and by reference number 635, storage volume driverA can request an attachment. For example, storage volume driver A canrequest to attach to the storage volume that was previously attached tocomputing node 2. As shown by reference number 640, the server-side datamanager can obtain storage information from the set of storage nodes224. For example, the server-side data manager can communicate with theparticular storage node 224 that was previously providing the storagevolume to computing node 2, and can obtain the storage informationassociated with the storage volume. As shown by reference number 645,the container manager can receive the storage information from theserver-side data manager.

As shown by reference number 650, the container manager can execute astorage installation procedure. For example, the container manager canattach the storage volume to the computing node 222 that is requestingto host the stateful microservices application (e.g., computing node 1)using the IP address and/or the port identifier associated with theparticular storage node 224. In this case, the container manager cangenerate a file system on the storage volume based on the attachment.Additionally, the container manager can mount the storage volume to theoperating system of the computing node 222 that is requesting to hostthe stateful microservices application, and can mount the storage volumeto a container associated with the computing node 222. Furthermore, thecontainer manager can notify the stateful microservices application thatthe attachment procedure has completed.

By utilizing the container manager to attach and mount the storagevolume, computing node 222 provides containerized persistent datastorage for a stateful microservices application. Additionally, thestateful microservices application can be hosted as-is (e.g., withoutuse of a plugin), thereby providing persistent data without requiringany changes to the stateful microservices application.

As indicated above, FIGS. 6A-6C are provided merely as an example. Otherexamples are possible and can differ from what was described with regardto FIGS. 6A-6C.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold can refer to a value beinggreater than the threshold, more than the threshold, higher than thethreshold, greater than or equal to the threshold, less than thethreshold, fewer than the threshold, lower than the threshold, less thanor equal to the threshold, equal to the threshold, etc.

To the extent the aforementioned embodiments collect, store, or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods, described herein, canbe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A device in a microservices management platform,comprising: a memory; and one or more processors to: receive, at aclient manager or client-side data manager, a specification identifyinginformation associated with a stateful microservices application;generate a request for storage information, including a microservicesapplication identifier associated with the stateful microservicesapplication based on the information included in the specification;provide the request, to a server-side data manager within themicroservices management platform, for the storage informationassociated with the stateful microservices application based on theinformation included in the specification, the storage informationincluding information associated with mounting a storage volume, theinformation including a port identifier associated with a storage node,of a set of storage nodes, to provide data storage for the statefulmicroservices application and metadata indicating a quantity of dataavailable for storage, the request to cause the server-side data managerto determine that the stateful microservices application is requestingstorage information for a first time by comparing the microservicesapplication identifier with a data structure comprising a plurality ofmicroservices application identifiers, the server-side data managerobtaining the storage information from the storage node; receive, fromthe server-side data manager, the storage information based on providingthe request; execute a storage installation procedure to provide thestateful microservices application with the storage volume based onreceiving the storage information, the storage volume to allow trafficto flow from the device to the storage node; and provide a notificationthat the stateful microservices application is available for deploymenton the device based on executing the storage installation procedure. 2.The device of claim 1, where the information included in thespecification include at least one of: a microservices applicationidentifier, a host internet protocol (IP) address, a value indicating aquantity of data for supporting the stateful microservices application,a file path, information identifying a storage volume driver, or astorage location within a container.
 3. The device of claim 1, where thestorage information includes at least one of: an internet protocol (IP)address of the storage node that has been selected to provide storage,or a storage networking protocol for managing data associated with thestorage volume.
 4. The device of claim 1, where the one or moreprocessors are further to: provide another request for additionalstorage information to a storage management node, the server-side datamanager hosted by the storage management node the other request to causethe storage management node to determine that the stateful microservicesapplication is deployed on another node and detach the storage volumefrom the other node based on determining that the stateful microservicesapplication is deployed on the other node; and receive, from the storagemanagement node, an indication that the storage volume is detached fromthe other node; and provide, to the storage management node, a requestto attach to the storage volume, the request to attach to cause thestorage management node to obtain the storage information.
 5. The deviceof claim 1, where the one or more processors, when executing the storageinstallation procedure, are to: establish a path between the device andthe storage node that is hosting the storage volume, and mount thestorage volume based on establishing the path.
 6. The device of claim 1,where the one or more processors, when executing the storageinstallation procedure, are to: attach the storage volume to the device,generate a file system on the storage volume based on attaching thestorage volume to the device, mount the storage volume to an operatingsystem of the device based on generating the file system, and mount thestorage volume to a container of the device based on mounting thestorage volume to the operating system of the device.
 7. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors in a microservices management platform, cause theone or more processors to: generate, at a client manager or client-sidedata manager, a request for storage information, including amicroservices application identifier, associated with a statefulmicroservices application, provide the request, to a server-side datamanager within the microservices managements platform, for the storageinformation associated with the stateful microservices application basedon information included in a specification, the storage informationincluding information associated with mounting a storage volume, theinformation including a port identifier associated with a storage node,from a set of storage nodes, to provide data storage for the statefulmicroservices application and metadata indicating a quantity of dataavailable for storage, the request to cause a storage management node toobtain the storage information, the request to cause the server-sidedata manager to determine that the stateful microservices application isrequesting storage information for a first time by comparing themicroservices application identifier with a data structure comprising aplurality of microservices application identifiers, the server-side datamanager obtaining the storage information from the storage node;receive, from the storage management node, the storage information basedon providing the request; execute a storage installation procedure toprovide the stateful microservices application with storage based onreceiving the storage information, the storage installation procedure touse the storage information to mount the storage volume that is capableof providing persistent data storage; and provide a notification, to thestateful microservices application, that the storage volume is mountedbased on executing the storage installation procedure.
 8. Thenon-transitory computer-readable medium of claim 7, where the statefulmicroservices application includes a plugin to allow the statefulmicroservices application to interact with a client-side data manager,and where the specification includes at least one of: a microservicesapplication identifier, a host internet protocol (IP) address, a valueindicating a quantity of data for supporting the stateful microservicesapplication, or a file path.
 9. The non-transitory computer-readablemedium of claim 7, where the one or more instructions, when executed bythe one or more processors, further cause the one or more processors to:receive an indication that the stateful microservices application hasbeen deployed; receive traffic associated with a client device writingdata to the storage volume; determine that the traffic satisfies athreshold; provide another request, to the storage management node, foradditional storage information, the other request to cause the storagemanagement node to obtain additional storage information from the set ofstorage nodes; receive, from the storage management node, the additionalstorage information; and execute another storage installation procedureto attach another storage volume to a device associated with the one ormore processors and to mount the other storage volume.
 10. Thenon-transitory computer-readable medium of claim 7, where the one ormore instructions, that cause the one or more processors to provide therequest for the storage information, cause the one or more processorsto: provide the request for the storage information to the storagemanagement node, the request to cause the storage management node toanalyze the set of storage nodes to determine that the storage volume isavailable; where the one or more instructions, that cause the one ormore processors to receive the storage information, cause the one ormore processors to: receive an internet protocol (IP) address and theport identifier associated with the storage node; and where the one ormore instructions, that cause the one or more processors to execute thestorage installation procedure, cause the one or more processors to:attach the storage volume based on the IP address and the portidentifier associated with the storage node, and mount the storagevolume based on attaching the storage volume.
 11. The non-transitorycomputer-readable medium of claim 7, where the one or more instructions,that further cause the one or more processors to: provide anotherrequest for the storage information to the storage management node, theother request to cause the storage management node to determine that thestateful microservices application is deployed to another node, todetach the storage volume from the other node based on determining thatthe stateful microservices application is deployed to the other node,and to obtain the storage information of the storage node based ondetaching the storage volume from the other node; receive an internetprotocol (IP) address or the port identifier associated with the storagenode; and attach the storage volume based on the IP address or the portidentifier associated with the storage node, and mount the storagevolume based on attaching the storage volume.
 12. The non-transitorycomputer-readable medium of claim 7, where the one or more instructions,that cause the one or more processors to execute the storageinstallation procedure, cause the one or more processors to: establish apath to the storage node that is hosting the storage volume, the path toallow traffic associated with the storage volume to be sent to alocation within the storage node that is hosting the storage volume, andmount the storage volume based on establishing the path.
 13. A method,comprising: receiving, by a container manager or client-side datamanager in a device in a microservices management platform, aspecification that identifies information associated with a statefulmicroservices application; generating, by the device, a request forstorage information, including a microservices application identifier,associated with a stateful microservices application based oninformation in the specification; providing, by the device, the request,to a server-side data manager within the microservices managementplatform, for storage information associated with the statefulmicroservices application based on the information included in thespecification, the storage information including information associatedwith mounting a storage volume, the information including a portidentifier associated with a storage node, of a set of storage nodes, toprovide data storage for the stateful microservices application andmetadata indicating a quantity of data available for storage, therequest to cause a storage management node to obtain the storageinformation from the set of storage nodes the request to cause theserver-side data manager to determine that the stateful microservicesapplication is requesting storage information for a first time bycomparing the microservices application identifier with a data structurecomprising a plurality of microservices application identifiers, theserver-side data manager obtaining the storage information from thestorage node; receiving, by the device and from the storage managementnode, the storage information based on providing the request; executing,by the device, a storage installation procedure to provide the statefulmicroservices application with storage based on receiving the storageinformation, the storage installation procedure to use the storageinformation to attach the storage volume to the device and to mount thestorage volume, the storage volume to allow traffic to flow from thedevice to the storage node; and providing, by the device and to a clientdevice, a notification that the stateful microservices application isavailable for deployment on the device based on executing the storageinstallation procedure.
 14. The method of claim 13, where the statefulmicro services application does not include a plugin and where thespecification includes at least one of: a microservices applicationidentifier, information identifying a storage volume driver, a valueindicating a quantity of data for supporting the stateful microservicesapplication, or a storage location within a container used to supportthe stateful microservices application.
 15. The method of claim 13,further comprising: receiving an indication that the statefulmicroservices application has been deployed; and receiving trafficassociated with the client device writing data to the storage volume.16. The method of claim 15, further comprising: determining that thetraffic associated with the client device satisfies a threshold;providing another request, to the storage management node, foradditional storage information, the other request to cause the storagemanagement node to obtain the additional storage information from theset of storage nodes; receiving, from the storage management node, theadditional storage information; and executing another storageinstallation procedure to attach another storage volume to the deviceand to mount the other storage volume.
 17. The method of claim 13, whereproviding the request for the storage information comprises: providingthe request for the storage information to the storage management node,the request to cause the storage management node to analyze the set ofstorage nodes to determine that the storage is available and to obtainthe storage information from the storage node based on determining thatthe storage is available; where receiving the storage informationcomprises: receiving one or more of: an internet protocol (IP) address,or the port identifier associated with the storage node; and whereexecuting the storage installation procedure comprises: attaching thestorage volume to the device based on the one or more of the IP addressor the port identifier associated with the storage node, and mountingthe storage volume based on attaching the storage volume.
 18. The methodof claim 13, further comprising: providing another request for storageinformation to the storage management node, the other request to causethe storage management node to determine that the stateful microservicesapplication is deployed to another node, to detach the storage volumefrom the other node based on determining that the stateful microservicesapplication is deployed to the other node, and to obtain the storageinformation from the storage node based on detaching the storage volume;receiving one or more of: an internet protocol (IP) address, or the portidentifier associated with the storage node; attaching the storagevolume to the device based on the one of more of the IP address or theport identifier associated with the storage node; and mounting thestorage volume based on attaching the storage volume.
 19. The method ofclaim 13, where executing the storage installation procedure comprises:attaching the storage volume to the device using one or more of: aninternet protocol (IP) address, or the port identifier associated withthe storage node, generating a file system on the storage volume basedon attaching the storage volume to the device, mounting the storagevolume to an operating system of the device based on generating the filesystem, and mounting the storage volume to a container of the devicebased on mounting the storage volume to the operating system of thedevice.
 20. The device of claim 1, where the one or more processors arefurther to: receive an indication that the stateful microservicesapplication has been deployed; and receive traffic associated with aclient device writing data to the storage volume.